Skip to content

Require the TC Module Eval tool (April 2026)#110

Draft
maccabeelevine wants to merge 3 commits intofolio-org:masterfrom
maccabeelevine:license-eval-require-tool
Draft

Require the TC Module Eval tool (April 2026)#110
maccabeelevine wants to merge 3 commits intofolio-org:masterfrom
maccabeelevine:license-eval-require-tool

Conversation

@maccabeelevine
Copy link
Copy Markdown
Member

After six months of the TC Module Eval tool being available for third-party license evaluation, require its use in our module evaluation process. (As we do with Sonar.)

* org.marc4j:marc4j is allowed if appropriately labelled, even if it is LGPL-2.1-or-later
* org.hibernate.* is allowed if appropriately labelled, even if it is LGPL-2.1-or-later
* By [request of the Community Council](https://folio-org.atlassian.net/wiki/spaces/CC/pages/1243348996/2025-09-26+Community+Council+Meeting+Minutes+at+WOLFcon), and until that request changes, no additional LGPL-licensed dependencies will be allowed.
* [ ] Inclusion of third party dependencies complies with [ASF 3rd Party License Policy](https://apache.org/legal/resolved.html), as defined and reported by the [FOLIO Module Evaluator](https://github.com/folio-org/tc-module-eval) tool (2)
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be language in here somewhere (maybe a sub-bullet) that the tool itself is only required for languages that the tool supports. I.e. Golang folio-org/tc-module-eval#13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant